Skip to content

Remove pessimistic versioning in gem command output#9550

Merged
hsbt merged 1 commit into
ruby:masterfrom
jeremyevans:remove-pessismistic-versioning-in-gem-command-output
May 18, 2026
Merged

Remove pessimistic versioning in gem command output#9550
hsbt merged 1 commit into
ruby:masterfrom
jeremyevans:remove-pessismistic-versioning-in-gem-command-output

Conversation

@jeremyevans

Copy link
Copy Markdown
Contributor

What was the end-user or developer problem that led to this PR?

At the recent developer meeting, we discussed switching from using pessimistic versioning by default to using optimistic versioning by default.

What is your fix for the problem, implemented in this PR?

Switch examples to use >=2 instead of ~>2.0.0 (which is really terrible as you are limited to 2.0.x versions).

For the help output, show a simpler example with a single version restriction, before an example with multiple version restrictions.

Make sure the following tasks are checked

Switch examples to use `>=2` instead of `~>2.0.0` (which is really
terrible as you are limited to 2.0.x versions).

For the help output, show a simpler example with a single version
restriction, before an example with multiple version restrictions.

@hsbt hsbt left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

@hsbt hsbt merged commit 7a326f5 into ruby:master May 18, 2026
93 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants